From Contract To Delivery, A Detailed Explanation Of The Project Management Process Of Joji Nakata (japanese Server)

1. contract signing and demand confirmation

confirmation of requirements before signing a contract is the key to project success.
- clarify the project roles: customer (joji nakata), project manager, operation and maintenance engineer, network security engineer.
- determine the service scope: vps/dedicated host, bandwidth, number of ips, cdn nodes, ddos protection level.
- sla indicators: availability 99.9%, response time within 1 hour, recovery time within 4 hours.
- cost and billing: monthly/yearly billing, billing rules for excess bandwidth, and additional protection fees.
- output documents: requirement specification, quotation, delivery schedule and acceptance criteria.

2. procurement and resource planning

resource planning should be based on traffic and load estimates to avoid resource waste or shortage.
- select a data center: tokyo, osaka or hokkaido node.
- server type: vps (virtual machine) or bare metal host, selected according to load.
- bandwidth planning: peak estimate is 500 mbps, reserve 30% capacity.
- ip and domain name: prepare public network ipv4 (2) and ipv6, domain name registration and whois information confirmation.
- contract terms: hardware replacement cycle, backup strategy, cross-region disaster recovery plan.

3. server configuration and image deployment

the deployment phase includes system imaging, network configuration and security baselines.
- operating system: ubuntu 22.04 lts or centos stream, selected based on application compatibility.
-basic software: nginx 1.24, mysql 8.0, redis 7, docker 24.
- security configuration: ssh port change, prohibit root direct connection, configure fail2ban.
- automated deployment: use ansible to write playbooks to achieve repeatable deployment.
- backup strategy: snapshot once a day, off-site backup once a week, retain 30-day version.

4. cdn and domain name resolution strategy

cdn and dns design affects access latency and resistance to attacks.
- cdn selection: domestic and foreign hybrid, mainly tokyo nodes, global back-to-source optimization.
- caching rules: static resources are cached for 30 days, api interfaces are not cached or cached briefly.
- dns design: primary dns and secondary dns, ttl is set to 300 seconds to facilitate fast switching.
- ssl/tls: enable let's encrypt or commercial certificate, enable http/2.
- traffic monitoring: configure real-time access monitoring and cdn cache hit rate alarm.

5. ddos defense and security drill

ddos protection is a step that must be verified before going online.
- protection level: basic cleaning 10 gbps, upgrade to 100 gbps on demand.
- policy configuration: rate limit, connection limit, black and white list, geo-ip filtering.
- drill plan: carry out quarterly stress testing and recovery verification.
- logs and alarms: connect to siem and set threshold alarms for abnormal traffic and number of connections.
- supplier sla: response within 15 minutes after protection is triggered, and cleaning completed within 1 hour.

6. testing and acceptance

the acceptance criteria are based on the sla and functional requirements specified in the contract.
- performance test: simulation of 10,000 concurrent connections, page p95 response < 500 ms.
- availability test: simulate outage failure and verify automatic switching and recovery time.
- security testing: basic penetration testing and vulnerability scanning, with a 100% repair rate.
- compatibility test: dns resolution consistency test of nodes in different regions.
- acceptance and delivery: acceptance report, system delivery documents, operation and maintenance manual and emergency plan.

7. delivery and operation and maintenance handover (including configuration examples)

a complete configuration list and real test data are provided upon delivery for customer confirmation.
- delivery list: server specifications, ip/domain name, cdn configuration, backup strategy, sla document.
- operation and maintenance handover: operation and maintenance account, monitoring authority, emergency contact information and process.
- real case: the nakata rangji project will be delivered in march 2025, with a peak traffic of 320 mbps and 99.95% availability in the first month.
- configure the sample table (sample data): see the table below.

project	configuration/value	illustrate
host	bare metal 8 cores/32gb/nvme 1tb	tokyo computer room, suitable for high i/o applications
bandwidth	1 gbps guaranteed, peak cleaning 100 gbps	contains high ddos defense capabilities
ip	2 x ipv4/ipv6 for the whole network	public network access and reverse proxy use
cdn	global nodes + tokyo optimization	static cache hit rate 88% (test value)
delay	domestic to tokyo average 120 ms	user experience baseline test results

- follow-up support: provide 7x24 operation and maintenance support package and regular security audits.